Systems for dynamic location-based account updates

ABSTRACT

Systems and methods for confirming and/or updating account information are disclosed. The systems and methods may calculate relocation scores based on transaction data and device location data. The relocation scores may be based on locations of the transactions and/or locations of a user device beyond a registered customer address. A relocation score can be calculated based on a quantity of transactions having transaction locations beyond a first predetermined distance from the customer address as determined by transaction location identifiers. A relocation score can be calculated based on an elapsed duration of time since a customer transaction was completed within the first predetermined distance from the customer address.

FIELD

The present disclosure relates generally to systems and methods foranalyzing trends in customer data to identify if customers have movedand, more particularly, to systems and methods for dynamicallyconfirming and/or updating accounts based on transaction and devicelocation data.

BACKGROUND

Current and accurate customer account information is important in acustomer/provider relationship. This is particularly true when thecustomer/provider relationship includes recurring services (e.g., forutilities, childcare, banking or credit cards, etc.) and, in turn,communications such as monthly bills and statements. On the customerside, current and accurate customer information, such as customeraddress, is important to ensure the customer is receiving allcommunications from the provider, including the monthly bills orstatements. If the customer does not receive this information because itwas mailed to the wrong address, there is a chance the customer may fallbehind in payments or, in some scenarios, someone else may receive thecommunication, which may increase the potential for fraud. This problemis only exacerbated when the customer is not digitally engaged, forexample those customers that rely on paper bills/statements mailed totheir current mailing address.

On the provider side, current and accurate account information isimportant to protect the provider's interests, such as ensuringcontinued receipt of payments and avoiding liability and customerservice concerns associated with potential fraud. Rather thanautomatically detecting when a customer has moved, existing systems tendto rely on manual procedures such as calling a customer if payment hasnot been received in a period of time, e.g., several months. However,with this and similar methods, contact is only made after thecommunication failure has occurred. These and other concerns exist.

BRIEF SUMMARY OF THE INVENTION

Examples of the present disclosure systems and methods for dynamicallyconfirming and/or updating accounts based on transaction and devicelocation data. The present disclosure provides a system for confirmingand/or updating account information. The system can be used to determineif a user has potentially moved from their registered customer addressand thus may be missing critical mailing communications. The system maycalculate relocation scores based on transaction data and devicelocation data. For example, a system can store customer accountinformation including a customer address, and receive transaction dataassociated with a plurality of customer transactions and containinglocation identifiers. Alternatively or additionally, the system mayreceive device location data associated with a customer device (e.g.,using a geographic location sensor on the customer device). Using thetransaction location identifiers and/or the device location data, thesystem can calculate a relocation score based on the device locationdata and the transaction data. If the relocation score is determined tobe over a predetermined value, the system can transmit a notification tothe user device seeking confirmation of the account information.

Various factors for calculating the relocation score are provided. Thesefactors can include determining how long transactions are outside of apredetermined distance from the customer address (e.g., a radius fromthe known address). The factors can also include whether payments madeto an account (e.g., payments made to cover a credit card statement) aremade by a financial institution that is not present within the region ofthe registered customer address. Various other example factors areprovided herein.

These and other aspects of the present disclosure are described in theDetailed Description below and the accompanying figures. Other aspectsand features of examples of the present disclosure will become apparentto those of ordinary skill in the art upon reviewing the followingdescription of specific, exemplary examples of the present invention inconcert with the figures. While features of the present disclosure canbe discussed relative to certain examples and figures, all examples ofthe present disclosure can include one or more of the features discussedherein. Further, while one or more examples can be discussed as havingcertain advantageous features, one or more of such features can also beused with the various examples of the invention discussed herein. Insimilar fashion, while exemplary examples can be discussed below asdevice, system, or method examples, it is to be understood that suchexemplary examples can be implemented in various devices, systems, andmethods of the present invention.

BRIEF DESCRIPTION OF THE DRAWINGS

The accompanying drawings, which are incorporated in and constitute apart of this specification, illustrate multiple examples of thepresently disclosed subject matter and serve to explain the principlesof the presently disclosed subject matter. The drawings are not intendedto limit the scope of the presently disclosed subject matter in anymanner In the drawings:

FIG. 1 is a diagram of an example system that can be used to implementone or more examples of the present disclosure;

FIG. 2 is a component diagram of an example user device, according tothe present disclosure;

FIG. 3 is a flowchart of an example process for confirming and/orupdating account information, according to the present disclosure;

FIGS. 4A-4D depict factors that can be used in determining a relocationscore, according to the present disclosure;

FIG. 5 is an example algorithm for determining a relocation score,according to the present disclosure;

FIG. 6 is a flowchart of an example method for confirming and/orupdating account information, according to the present disclosure; and

FIG. 7 is a process of an example process for confirming and/or updatingaccount information, according to the present disclosure.

DETAILED DESCRIPTION

Examples of the present disclosure generally relate to systems andmethods for analyzing trends in customer data to identify if customershave moved and, more particularly, to systems and methods fordynamically confirming and/or updating accounts based on transaction anddevice location data. The systems and methods described herein arenecessarily rooted in computer technology as they relate to digitallytracking customer location based on digital payment locations (e.g.,point of sale (PoS) locations in card-present transactions or internetprotocol (IP) addresses in card-not-present transactions) and devicelocations. This type of location-based technology is facilitated by andrelies on the use of the digital payment and tracking systems describedherein.

Maintaining accurate account information for customers, includingcustomer address, is an important function for both providers andcustomers alike. Throughout this disclosure, examples are provided inthe context of financial institutions, such as banks and/or credit cardproviders. However, the interest in maintaining accurate accountinformation is not limited to financial institutions—and the systems andmethods herein can apply to other settings. However, one aspect of thepresent disclosure provides the ability to identify where transactionsare occurring, e.g., via PoS device location, IP addresses, etc. Forthese examples, the systems and methods are well-suited for thefinancial institutions to analyze trends in customer data.

Throughout this disclosure reference is made to a “relocation score.” Itwill be understood that the score can be understood as a certaintyand/or confidence level for whether a customer has changed addresses.Examples are provided in which a stakeholder (like a financialinstitution) can adjust the relocation score according to personalizedinputs—e.g., types of purchases made, how far the purchases are madefrom a known customer address, etc. However, it will also be understoodthat the bounds of the relocation score can be adjusted based onneed—with different types of data getting more weight than other typesof data. To illustrate, it may be that a particular stakeholder findscard-not-present transactions to be the most indicative of a customermoving, instead of card-present transactions. In those cases, thestakeholder can tailor those indicators to adjust the relocation scorethe most.

Reference will now be made in detail to exemplary examples of thedisclosed technology, examples of which are illustrated in theaccompanying drawings and disclosed herein. Wherever convenient, thesame reference numbers will be used throughout the drawings to refer tothe same or like parts.

FIG. 1 is a diagram of an example system environment 100 that can beused to implement one or more examples of the present disclosure. A moredetailed explanation of the components of the system environment 100 isprovided below. It is beneficial, however, to provide a brief overviewto describe the components of the systems and methods for dynamicallyconfirming and/or updating accounts based on transaction and devicelocation data. The system environment 100 can include a backend system106. The backend system 106 can be associated with the entity thatstores customer account information, such as a financial institution.The backend system 106 can also store customer account information,billing information, transaction data, etc. The backend system 106 canbe positioned communicatively between a transaction system 104 and adevice 102, such as a user device of a customer with an account with thefinancial institution. The backend system 106 can receive transactionrequests from a transaction system 104, track user location informationon the device 102, and the like.

The system environment 100 can also include a transaction system 104.The transaction system 104 can be associated with a goods or servicesprovider. The transaction system 104 can communicate with the backendsystem 106 so as to transmit payment requests from a customer regardingan intended purchase. The transaction system 104 can be associated withbrick and mortar stores, such that transactions include card-presenttransactions; and/or the transaction system 104 can be associated withdigital retailers, such that transactions include card-not-presenttransactions. In some examples, the transaction system 104 can becommunicably coupled with a point of sale (PoS) device, as will bedescribed in greater detail herein.

The backend system 106, transaction system 104, and device 102 cancommunicate with each other over a wired or wireless network 108. Thenetwork 108 can, therefore, facilitate a transaction being made via thetransaction system 104 by a user using a card, by a user making anonline purchase, and the like. The network 108 can facilitate thepayment requests that are sent to the backend system 106 to initiatepayment to the transaction system 104. The network 108 can alsofacilitate information sharing between the device 102 and the backendsystem 106. For example, as will be described in greater detail below,the user device can operate a mobile application (e.g., mobileapplication 250) that is associated with the backend system 106 (i.e.,with the financial institution that operates the backend system). Thebackend system 106 can utilize the mobile application 250 to locatewhere the device 102 over certain periods of times to help determine ifthe device 102 is regularly or consistently outside of a predetermineddistance from the known customer address.

The system environment 100 shown in FIG. 1 can form a system inclusiveof the backend system 106, transaction system 104, and user device 102,or at least some or all of the components of the backend system 106,transaction system 104, and user device 102. For example, in certainembodiments described herein, the backend system 106 can rely uponoperating systems and/or native mobile applications (e.g., mobileapplication 250) operating on the device 102 to track movement of theuser via the location services provided by the device 102. The device102, in turn, can include a geographic location sensor (“GLS”) 214 fordetermining the geographic location of the device 102, including forexample global positioning system (GPS) tracking sensor(s), cellulartracking sensor(s), and the like. The use of the backend system 106hardware/software in tandem with the device 102 hardware/software cantherefore provide the location tracking capabilities of the presentsystems and methods. In addition, the transaction system 104 can includehardware/software that enables each transaction made by a financialinstitution customer to be tracked—be it via PoS device locationtracking and/or IP address location tracking. The use of the backendsystem 106 hardware/software in tandem with the transaction system 104hardware/software can therefore provide additional location trackingcapabilities to the present systems and methods.

FIG. 2 is a component diagram of an example device 102, according to thepresent disclosure. The device 102 can be a mobile computing device(e.g., a smart phone, tablet computer, smart wearable (e.g., a smartwatch), portable laptop computer, voice command device, wearableaugmented reality device, or other mobile computing device) or astationary device (e.g., desktop computer). The device 102 can include aprocessor 202 and a memory 204, operating system (“OS”) 206, one or moreprograms (e.g., mobile application 250 described below), and/or datastorage 208. The device 102 can also include a communication interface216 that includes a transceiver 218. The communication interface 216and/or transceiver 218 can be used to transmit and/or receive the datadescribed throughout this disclosure, including for example theshort-range wireless connections, payment tokens, transaction locationdata, etc.

The device 102 can also include one or more input/output (“I/O”) devices210 that can include one or more interfaces for receiving signals orinput from devices and providing signals or output to one or moredevices that allow data to be received and/or transmitted by the device102. For example, the device 102 can include interface components, whichcan provide interfaces to one or more input devices, such as one or morekeyboards, mouse devices, touch screens, track pads, trackballs, scrollwheels, digital cameras, microphones, sensors, and the like, that allowthe device 102 to receive data from one or more users.

The device 102 can also include a user interface (“U/I”) device 212 forreceiving user input data, such as data representative of a click, ascroll, a tap, a press, or typing on an input device that can detecttactile inputs. According to some examples, U/I device 212 can includesome or all of the components described with respect to I/O device 210above. The U/I device 212 can be defined as the “input” of the device102. The device 102 can also include a GLS 214 for determining thegeographic location of the device 102, including by using GPS data andcellular data, as described above.

The device 102 can include a display 220. The display 220 can providevisual representation of the applications (e.g., mobile application 250)and/or graphical user interfaces (GUIs) associated with thoseapplications. The display 220 can also be a U/I device 212 in the casethat the device 102 has touchscreen capabilities. In other words, insome examples the display 220 can be the “input” of the device 102.

FIG. 3 is a flowchart of an example process 300 for confirming and/orupdating account information, according to the present disclosure.Process 300 can be performed in whole or in part by the components ofthe backend system 106, for example a processor 112, memory 114, andinstructions (e.g., OS 116 and program 118) described below. Process 300can begin with storing 305, in a database associated with the system(e.g., database 120), customer account information including a customeraddress. The customer address can be stored for the account when thecustomer sets up their account (e.g., backing account, credit cardaccount, etc.). The customer address can be revised by accessing theaccount via the backend system 106 and changing the account. In manycases, however, customer may forget to make changes to addresses whenthey move. The present systems and methods, therefore, enable thebackend system 106 to determine if the user has inadvertently forgottento change addresses after a move so that bills/statements can bererouted to a different address.

Process 300 can include receiving 310 transaction data associated with aplurality of customer transactions. The transaction data can be receivedfrom a variety of sources. In one example, the transaction data can bereceived from a transaction system (e.g., transaction system 104) via aPoS device (e.g., PoS device 130) associated with or in communicationwith the transaction system 104. For example, the PoS can be anelectronic fund transfer terminal that accepts payments via a creditcard via a magnetic stripe and/or via contactless payment. In someexamples, the transaction data can be received from the transactionsystem 104 via a computing device owned by the account holder (e.g.,device 102). For example, when a user is purchasing a product/servicefrom an online retailer via the internet and/or a mobile application,the transaction system 104 processing can transmit that purchaseinformation to the backend system 106.

The transaction data described in the receiving 310 step can includetransaction location identifiers associated with at least a portion ofthe plurality of customer transactions. These location identifiers canbe retrieved along with the transaction from the transaction system 104.In the context of card present transactions, the transaction locationidentifiers can be received in view of the location of the PoS device.PoS devices are registered to a company, and the transfer of funds isfinancial institution-to-financial institution. Therefore, thetransaction information includes certain information, including but notlimited to date, time, transaction number, and transfer location—whichincludes the location of the PoS device when the card-in-hardtransaction was made. In the context of online purchases, thetransaction location identifiers can be found via identifying the IPaddress of the device that made the purchase. In these scenarios, thefinancial institution operating the backend system 106 can have anegotiated partnership with online retailers such that the financialintuition can receive information about the IP address of the purchaser.

In other examples, the IP address can also be received if a “virtualnumber” is used for the transaction. A virtual number, or a virtual cardnumber, is a process/system to make a purchase online without using abank card number. Instead of using the bank card number, the financialinstitution can provide a merchant-specific virtual number that ismapped to a bank account and that can only be used at that boundmerchant Using the virtual number can provide information on where thetransaction was made (i.e., via the IP address). To illustrate, thebackend system 106 can know the IP address of the device that createdthe virtual number. A user device (e.g., device 102) can, for example,include a browser extension that can communicate with the mobileapplication 250 and/or OS 206 of the device 102. The browser extensioncan be activated when a checkout page is accessed on the device 102. Thebrowser extension can ask the customer if they wish to create a virtualnumber. If the customer agrees, the browser extension can interact withthe backend system 106 to create the virtual number. The device 102 canreceive the virtual number, and the virtual number can be displayed inthe browser extension. In a checkout page, the customer can enter thevirtual number into the checkout fields and confirm purchase. Thebackend system 106 can store the IP address of the device that createdthe virtual number, and the backend system 106 can store which merchantis bound to the virtual number. This use of the virtual number can serveas a proxy for the IP where the customer made the purchase.

In some examples, process 300 can include receiving 315 device (e.g.,device 102) location data associated with the device 102. The backendsystem 106, for example, can use a mobile application (e.g., mobileapplication 250) operating on the phone to locate where the phone hasbeen located over a predetermined period of time. As will beappreciated, location services on a device 102 can be employed toperiodically ping a device to identify customer movement/location.

Process 300 can include calculating 320 a relocation score based on thetransaction data and/or device location data. Example parameters thatcan be used to calculate a relocation score are found in FIGS. 4A-4D.However, to briefly summarize, the relocation score can be based on (1)a quantity of transactions of the plurality of customer transactionhaving transaction locations beyond a first predetermined distance fromthe customer address as determined by the transaction locationidentifiers, and/or (2) an elapsed duration of time since a customertransaction of the plurality of customer transactions was completedwithin the first predetermined distance from the customer address. Forparameter (1) above, the location of the transactions can be used todetermine if there is a likelihood the customer moved and thus ispotentially not receiving statements. As will be described in greaterdetail below with reference to FIG. 4A, this location can be based onwhere the customer “typically” is located—i.e., the registered customeraddress. For example, if the customer has a registered address in NewYork City, the first predetermined distance from the customer addressthat may increase the relocation score may be relatively small—15 milesfor example. This is because ordinary movement for this particularcustomer may be restricted to the New York City area and a 15 mileradius from their current address is a significant distance. However, ifthe customer has a customer address in rural Tennessee, the firstpredetermined distance that raises concerns about potential moving canbe larger—50 miles for example. In some examples, the distance can bescaled based on customer transactions over a period of time. Forexample, if a user makes all purchases over a six-month period within a63-mile radius from home, the first predetermined distance can be 63miles until it is updated after another six months. For parameter (2)above, the elapsed duration of time since a customer transaction wascompleted within the first predetermined distance can act as a “reset”that shows the customer may not have moved. For example, if a customermakes purchases outside of the first predetermined distance consistentlyfor three months, without any “resets” where a transaction was completedwithin the first predetermined distance, the likelihood of relocationcan be higher, thus a higher relocation score. However, if the customeralso completed a purchase within that first predetermined distance a fewtimes within those three months, it could be that the customer wasmerely traveling. The same type of scoring described in parameters (1)and (2) can be performed using the device location information. It willalso be appreciated that the relocation score can be determined based oneither the transaction data, the relocation data, or both.

Process 300 can include determining 325 if the relocation score is abovea predetermined value. The predetermined value can be set based onpreferences set by the financial institution. If the relocation score isbelow the predetermined value, process 300 can end. If the relocationscore is above the predetermined value, process 300 can includetransmitting 330, for example via transceiver 124, a notification to theuser device seeking confirmation of the account information. Thisnotification can be any number of notifications, including automaticpush notifications, automatic text (e.g., SMS) messages, automaticemails, automatic calls, and/or personalized calls from a customerservice representative. Further, remedial actions can be performed.Examples of the notifications and remedial measures are provided in thedescription with respect to FIG. 5 . Process 300 can end after thetransmitting 330 step or any other processes described herein can becompleted.

FIGS. 4A-4D depict factors that can be used in determining a relocationscore, according to the present disclosure. As indicated in each ofFIGS. 4A-4D, these factors can form all or a portion of the calculating320 step described in process 300 of FIG. 3 . Referring to FIG. 4A, thesystem (e.g., backend system 106 and/or a processor associated with thebackend system 106 such as processor 112) can receive transactionlocation information, as described above, for a plurality oftransactions. These transactions can be performed, for example, at a PoSdevice and/or on a device (e.g., device 102). The backend system 106 canthen determine 402 if these transactions have occurred beyond a firstdistance from the registered customer address. If the transaction dataindicates that the transactions were completed outside of the firstdistance, the system can increase 404 the relocation score; if notransactions were completed outside of the first distance, the systemcan decrease 406 the relocation score or leave the score the same. Asstated above, the distance (e.g., radius) can be set based on the typeof location of the registered customer address—urban registeredaddresses can have a shorter distance to trigger increasing therelocation score, while rural registered addresses can have a longerdistance to trigger increasing the relocation score.

Further, the determining 402 step in FIG. 4A can be based ontransactions over a certain period of time. For example, if transactionsoccur outside of the distance over the course of two weeks or even onemonth, this may not be sufficient to trigger increasing the relocationscore, since it may be that the customer was merely travelling. Thefinancial institution can therefore set a time period in which to trackthe distant transactions, e.g., two months, three months, etc. Further,the time period in which to track the distant transactions can also betailored based on customer information related to, for example, jobtitle or job description. The financial institution can query thecustomer (e.g., via mobile application 250) about what type of jobs thecustomer holds. If the customer is a consultant, pilot, long-haul truckdriver, etc., the time period to trigger increasing the relocation scorecan be scaled longer. Further, if it is determined that the customer isactive military, the duration of time can be increased and/or therelocation score calculation can be paused completely when the customeris deployed. It can be possible for the financial institution to receiveand retain this type of information in accordance with compliance withtheir Servicemembers Civil Relief Act (SCRA) duties.

Referring to FIG. 4B, the system (e.g., backend system 106 and/or aprocessor associated with the backend system 106 such as processor 112)can determine 408 if any transaction of the plurality of transactionfrom FIG. 4A was made within the distance from the customer addresswithin an elapsed period of time. If one (or more) transactions weremade within that distance (radius) during the elapsed period of time,the system can decrease 412 the relocation score; if no transactionswere within that distance (radius) during the elapsed period of time,the system can increase 410 the relocation score. Again, thisdetermining 408 step can be used to “reset” the certainty that the usermay have a different mailing address because the customer transactedcloser to home. This can indicate, for example, that the customer wasmerely traveling when the plurality of transactions outside of the firstdistance were made. To illustrate, if the user completes 1000transactions outside of the predetermined distance over the course ofthree months, but completes 5 transactions inside the predetermineddistance during that time, the relocation score can be decreased 412 or,in some examples, reset to zero (e.g., zero certainty that the customermoved).

Referring to FIG. 4C, the system (e.g., backend system 106 and/or aprocessor associated with the backend system 106 such as processor 112)can determine 414 if a user device (e.g., device 102) is beyond a seconddistance from the customer address over a duration of time. This“system” of tracking the device can include both the backend system 106and the device 102. If the device is outside of the second distance fora duration of time, the system can increase 416 the relocation score; ifthe device does not go outside the second distance for the duration oftime, the system can decrease 418 the relocation score. The system can,as described above, use the location services (e.g., GLS 214) of thedevice 102 to track the device location. In these examples, if thedevice is outside of the second distance for two months, three months,etc. without re-entering the second distance (e.g., radius), therelocation score can be increased. If the device re-enters the seconddistance, the relocation score can be decreased or, in some examples,reset to zero (e.g., zero certainty that the customer moved). It iscontemplated that the second distance described in FIG. 4C is the sameas the first distance described in FIG. 4A; though the second and firstdistance can also be different distances. By having a second distance(based on device location) that is different than the first distance,the backend system 106 can give more tolerance to people who traveloften during the day but do not make purchases/significant purchases,e.g., a larger radius can be applied to device location data.

Referring to FIG. 4D, the system (e.g., backend system 106 and/or aprocessor associated with the backend system 106 such as processor 112)can determine 420 if a balance payment for an account associated withthe customer is received via a check; if the address is different thanthe customer address, the relocation score can be adjusted. As will beappreciated, paper checks include identifying information such as nameand address. The system can use optical character recognition (OCR) onany check received, compare the name and address on the check withcustomer address information associated with the account which is beingbilled, and determine if the addresses match. If the address isdifferent than the customer address, the system can increase 422 therelocation score; if the address is the same, the system can decreasethe relocation score 424. To complete the OCR, the backend system 106can include or be in communication with an image capture device 150,which can be a camera, scanner, and the like capable of capturing and/orscanning the image of the check.

Another, similar example of using image-recognition to identify whetherthe relocation score should be increased or decreased is to scan,capture, and/or examine the envelope in which the check payment wasreturned to the financial institution. If the balance check was returnedto the customer within an envelope provided in the mailed, paperstatement, this is indicative of the customer receiving the paperbalance statements, and therefore is evidence that the customer has notmoved—the relocation score can be lowered. This information can becaptured by OCR, as described above. In some examples, the returnenvelope can include an identifying marker, such as a barcode, quickresponse (QR) code, alphanumeric code, and the like that can be scannedto indicate whether the customer returned the check in the providedenvelope.

In an additional or an alternative embodiment, the backend system 106can determine whether the relocation score should be increased ordecreased based on the value of the check. For example, if a balance onthe account is $125.36, and a check is returned to the financialinstitution with a value of $125.36, this can be indicative of the userreceiving the paper balance statement and sending a check. This examplecan be particularly valuable for customers that are not digitallyenrolled. For example the backend system 106 can store informationindicative of whether the customer (a) is actively enrolled in digitalaccount management systems associated with financial institution and/or(b) has accessed their digital account management system since a priorstatement period. If the customer is not digitally enrolled, or if thecustomer has not accessed their digital account since the laststatement, an indication that the customer paid the correct balance isevidence that the customer has not moved—and the relocation score can belowered. The value of the check can be scanned via the image capturedevice 150, as described above.

FIGS. 4A-4D depict example parameters/factors that can be used indetermining a relocation score, but the examples are not exhaustive orlimiting. Other factors can be used. For example, in some embodimentsthe system can analyze the type of good or service being purchased bythe customer to increase or decrease the relocation score. Thetransaction information received from the transaction system 104 caninclude a plurality of categories associated with the at least a portionof the plurality of customer transactions. These categories can bedetermined based on merchant category codes for the merchant operatingthe transaction system 104. Merchant category codes can be used todetermine if a customer is purchasing groceries, hardware, car rentals,etc. The type of category can be indicative of whether a customer hasmoved. For example, if the plurality of transactions over apredetermined period of time include a car rental, this can beindicative that the customer has not moved but is merely outside of thepredetermined distance for work, travel, etc.—and the relocation scorecan be decreased or can remain static. If the plurality of transactionsinclude hardware transactions, however, this can indicate that thecustomer has moved into a new home—and the relocation score can beincreased.

Other factors that can be used to increase or decrease the relocationscore can include what type of financial institution is being used tomake a statement payment. For example, in the case of a credit cardstatement, a user typically pays the statement via a checking account.If the financial institution associated with that checking accountchanges over time, that can be indicative of the customer moving. Toillustrate using an example, the customer may have an address inGeorgia, and the customer typically pays her credit card statement witha checking account at Bank A, which has a southeastern U.S. footprintwhen it comes to branch locations. If one month the customer makes apayment with a checking account at Bank B, that does not have asoutheastern footprint but only a midwestern footprint, this canindicate that the customer has moved, and her relocation score can beincreased.

FIG. 5 is an example algorithm for determining a relocation score,according to the present disclosure. Any of the factors described inFIGS. 4A-4D, or any other factor as described herein or otherwise, canbe used alone to determine a relocation score, or multiple factors canbe used to provide a sliding scale of relocation score and/or remedialaction based on the relocation score, as illustrated in FIG. 5 . Forexample, a Relocation Level 1 (or highest level) of a relocation scoreconfidence level can be when a check is received for a balance paymentthat includes a new customer address. When this happens, the relocationscore can be increased to a threshold that triggers a remedial action.These remedial actions can include placing a hold on the bill and havinga customer service agent call the customer device registered to thecustomer. Billing can be placed on hold, for example, to ensure that noone besides the customer is receiving the paper bill—thereforedecreasing chances of fraud.

Relocation Level 2 (or next highest level) of a relocation scoreconfidence level can be when balance payment is received from a regionalback that is beyond a predetermined distance from the customer address.This example was described above for when a bill payment is receivedfrom a checking account at a financial institution that does not havefootprint within a predetermined distance of the registered customeraddress. The remedial actions for these situations can include having acustomer service agent call the customer device. Relocation Level 3 (ornext highest level) of a relocation score confidence level can be whencard-present transactions occur over a predetermined time period andbeyond a predetermined distance from customer address. Again, thesesituations can “reset” the score, or the relocation score can belowered, if a transaction occurs within the distance within thepredetermined time. When the score reaches a predetermined level, theremedial action can include a customer service call to the customerdevice or an automated notification to the customer device. Theautomated notification can be a SMS message, text message, pushnotification (e.g., to the mobile application 250), an automated call,email, etc. Relocation Level 4 (or the lowest level) of a relocationscore confidence level can be when a user device (e.g., device 102) isbeyond a predetermined distance from the customer address over apredetermined period of time. Unlike Relocation Level 3, which uses thetransaction location data described herein, Relocation Level 4 uses thedevice location data. The remedial measure for this relocation level canbe an automated notification, as described above. Certain remedialactions can include automatically updating a user address in thecustomer account if the relocation score is high enough. In someexamples, a notification can be sent to the device 102 to confirmwhether the address should be updated, and the system can automaticallyupdate the customer address in response to confirmation. In someexamples, if the relocation score is sufficiently high, the backendsystem 106 can freeze the customer account so that no additionaltransaction can be made.

In some examples, the relocation scores can be tiered. For example, someembodiments of the present disclosure utilize both transaction locationdata as well as device location data. In these examples, a singlecustomer may achieve a certain relocation score—say a 50% likelihoodthat the customer has moved based on transaction location data alone.This 50% relocation score may be sufficient to send a push notificationif reached. If the system also tracks device location data, and thelocation of the device 102 is outside of a predetermined distance fromthe customer address, the location information can push the relocationscore beyond the 50% mark. The backend system 106 can set a threshold,for example, of 50% in which to send personal communications to thecustomer (e.g., a customer service call).

In some examples, any and all factors that are used to calculate arelocation score can be altered and/or recalibrated based on feedbacksent to the system. For example, a machine learning algorithm operatedby the backend system 106 can be used to update the parameters of theindividual factors used to calculate the score. Using the “card-presenttransactions over a predetermined period of time and beyond apredetermined distance from the client address” factor as an example,the backend system 106 can learn whether the predetermined parametersare sufficient to identify whether a customer has moved. To illustrateusing a non-limited example, consider that the backend system determinesthat 100 customers in Urban Area A have moved based on a relocationscore that uses a 50-mile distance (radius) parameter. After sendingthese 100 customers an automated notification to the client devices, thebackend system 106 receive 80 indications back from the customers thatthey have not moved from their registered customer address. Using thisinformation, the backend system 106 can re-train the machine learningalgorithm to reset that the radius that triggers an increased relocationscore to be 75 miles, so that the “false-positives” are decreased. Inaddition, the backend system 106 can train the machine learningalgorithm to weight certain activities more heavily based on responsesfrom users. For example, if it is determined that the “card-presenttransactions over a predetermined period of time and beyond apredetermined distance from the client address” factor is providing morefalse-positive of customers moving than “user device beyond apredetermined distance,” the user device location data can be weightedmore heavily for increasing the relocation score than the transactionlocation data. Further, information related to customer engagement withthe notifications sent to the customer devices can help train the typesof notifications sent. As described, the backend system 106 can have arelocation score threshold, for example 50% certainty, in which to sendpersonal communications to the customer. If it is determined thatcustomer interaction with automated notifications is low, the system canbe trained to send personal communications to the customer at a lowerrelocation score.

FIG. 6 is a flowchart of an example method 600 for confirming and/orupdating account information, according to the present disclosure.Method 600 can be performed in whole or in part by the components of thebackend system 106, for example a processor 112, memory 114, andinstructions (e.g., OS 116 and program 118) described below. Method 600can begin with storing 605, in a database (e.g., database 120)associated with the system, customer account information including acustomer address. Method 600 can include receiving 610, for example at atransceiver 124, transaction data associated with a plurality ofcustomer transactions. The transaction data can include transactionlocation identifiers associated with at least a portion of the pluralityof customer transactions.

The method 600 can include calculating 615 a relocation score. Asdescribed above, in some examples transaction location data can be usedto calculate the relocation score, in some examples the device locationdata can be used, and in some examples both transaction location dataand device location data can be used. In some examples, method 600 caninclude determining 620 if a quantity of transactions of the pluralityof customer transaction are made beyond a first distance from thecustomer address. Method 600 can include determining 625 whether anytransactions of the plurality of customer transactions are made withinthe first distance from the customer address during an elapsed period oftime. If the system determines in step 620 that a certain quantity oftransactions were made outside the distance (i.e., radius), anddetermines in step 625 that no transaction was made within the distanceduring the elapsed time period, method 600 can include transmitting 630,via the transceiver 124, a notification to a user device (e.g., device102) seeking confirmation of the account information. Method 600 can endafter step 630 or can include any other steps described herein.

FIG. 7 is a process of an example process 700 for confirming and/orupdating account information, according to the present disclosure.Process 700 can be performed in whole or in part by the components ofthe backend system 106, for example a processor 112, memory 114, andinstructions (e.g., OS 116 and program 118) described below. Process 700can begin with storing 705, in a database (e.g., database 120)associated with the one or more processors, customer account informationincluding a customer address. Process 700 can include calculating 710,via the one or more processors, a relocation score based on devicelocation data received from a user device and transaction data. Process700 can include receiving 715, at the one or more processors, anindication of a payment to a balance associated with the customeraccount information. The indication of the payment can be received via acheck. Process 700 can include performing 720, via the one or moreprocessors, optical character recognition (OCR) on the check to identifya check address. Process 700 can include updating 725, via the one ormore processors, the relocation score based on the check address.

After the relocation score is updated, the process 700 can includedetermining 730 whether the relocation score is above a predeterminedvalue. If the score is below the value, process 700 can end. If thescore is above the value, process 700 can include transmitting 735, viaa transceiver associated with the one or more processors, a notificationto the user device seeking confirmation of the account information whenthe relocation score is above a predetermined value. Other steps, suchas the remedial actions described with reference to FIG. 5 can also beperformed.

Referring again to the system environment 100 described in FIG. 1 , thebackend system 106 can include one or more processors 112, a memory 114,and data storage, for example in database 120. The processor 112 caninclude one or more of a microprocessor, microcontroller, digital signalprocessor, co-processor or the like or combinations thereof capable ofexecuting stored instructions and operating upon stored data.

The memory 114 of the backend system 106 can include, in someimplementations, one or more suitable types of memory (e.g., volatile ornon-volatile memory, random access memory (RAM), read only memory (ROM),programmable read-only memory (PROM), erasable programmable read-onlymemory (EPROM), electrically erasable programmable read-only memory(EEPROM), magnetic disks, optical disks, floppy disks, hard disks,removable cartridges, flash memory, a redundant array of independentdisks (RAID), and the like), for storing files including an operatingsystem, application programs (including, for example, a web browserapplication, a widget or gadget engine, and or other applications, asnecessary), executable instructions and data.

The memory 114 of the backend system 106 can contain an operating system(“OS”) 116 that can run one or more programs 118. The one or moreprograms 118 can perform one or more functions of the disclosedexamples. The one or more programs 118 can include, for example, aprogram for creating the mobile application 250 operable on the userdevices (e.g., device 102).

The memory 114 can also include any combination of one or moredatabases, including for example database 120, controlled by memorycontroller devices (e.g., server(s), etc.) or software, such as documentmanagement systems, Microsoft® SQL databases, SharePoint® databases,Oracle® databases, Sybase® databases, or other relational databases.

The backend system 106 can include a communication interface 122 forcommunicating with external systems or internal systems. Thecommunication interface 122 can include a serial port, a parallel port,a general-purpose input and output (GPIO) port, a game port, a universalserial bus (USB), a micro-USB port, a high definition multimedia (HDMI)port, a video port, an audio port, a Bluetooth™ port, an NFC port,another like communication interface, or any combination thereof. Thecommunication interface 122 can include a transceiver 124 to communicatewith compatible devices. A transceiver 124 can be compatible with one ormore of: RFID, NFC, Bluetooth™, low-energy Bluetooth™ (BLE), WiFi™,ZigBee™, ambient backscatter communications (ABC) protocols, or similartechnologies that allows the backend system 106 to communicate via thenetwork 110 described herein.

The transaction system 104 can include a processor 132, memory 134, anOS 136 operating one or more programs 138, a database 140, and acommunication interface 142 comprising a transceiver 144, each of whichcan be similar to the processor 112, memory 114, an OS 116 operating oneor more programs 118, a database 120, communication interface 122, andtransceiver 124 described above for the backend system 106,respectively.

The transaction system 104 can include or be communicatively coupled toa PoS device 130. PoS device 130 can provide the interface at what acard holder makes a payment to the merchant in exchange for goods orservices. PoS device 130 can include and/or cooperate with weighingscales, scanners, electronic and manual cash registers, electronic fundstransfer at point of sale (EFTPOS) terminals, touch screens and anyother wide variety of hardware and software available for use with PoSdevice 130. PoS device 130 may be a retail point of sale system and caninclude a cash register and/or cash register-like computer components toenable purchase transactions. PoS device 130 also can be a hospitalitypoint of sale system and include computerized systems incorporatingregisters, computers and peripheral equipment, usually on a computernetwork to be used in brick and mortar retailer, restaurant, hairsalons, hotels, or the like. PoS device 130 can be a wireless point ofsale device, for example a tablet computer that is configured to operateas a PoS device, including for example, software to cause the tabletcomputer to execute point of sale functionality and a card reader suchas for example the Capital One® SparkPay card reader, the Square®reader, Intuit's® GoPayment reader, or the like. PoS device 130 also canbe a cloud-based point of sale system that can be deployed as softwareas a service, which can be accessed directly from the internet using,for example, an internet browser.

While the present disclosure has been described in connection with aplurality of exemplary aspects, as illustrated in the various figuresand discussed above, it is understood that other similar aspects can beused, or modifications and additions can be made, to the describedaspects for performing the same function of the present disclosurewithout deviating therefrom. For example, in various aspects of thedisclosure, methods and compositions were described according to aspectsof the presently disclosed subject matter. However, other equivalentmethods or composition to these described aspects are also contemplatedby the teachings herein. Therefore, the present disclosure should not belimited to any single aspect, but rather construed in breadth and scopein accordance with the appended claims.

The components described in this disclosure as making up variouselements of the systems and methods are intended to be illustrative andnot restrictive. Many suitable components that would perform the same orsimilar functions as the components described herein are intended to beembraced within the scope of the disclosure. Such other components notdescribed herein can include, but are not limited to, for example,similar components that are developed after development of the presentlydisclosed subject matter.

Examples of the present disclosure can be implemented according to atleast the following clauses:

Clause 1. A system for confirming account information, comprising: oneor more processors; and memory in communication with the one or moreprocessors and storing instructions that, when executed by the one ormore processors, are configured to cause the system to: store, in adatabase associated with the system, customer account informationincluding a customer address; receive transaction data associated with aplurality of customer transactions, the transaction data includingtransaction location identifiers associated with at least a portion ofthe plurality of customer transactions; calculate a relocation scorebased on the transaction data, wherein the relocation score is basedupon at least one of: a quantity of transactions of the plurality ofcustomer transaction having transaction locations beyond a firstpredetermined distance from the customer address as determined by thetransaction location identifiers; or an elapsed duration of time since acustomer transaction of the plurality of customer transactions wascompleted within the first predetermined distance from the customeraddress; and transmit, via a transceiver associated with the system, anotification to a user device seeking confirmation of the accountinformation when the relocation score is above a predetermined value.

Clause 2. The system of Clause 1, wherein the instructions are furtherconfigured to cause the system to receive, from a geographic locationsensor on the user device, device location data associated with the userdevice, wherein the relocation score is further based on the devicelocation data, and wherein the relocation score is based upon a durationof time the user device is beyond a second predetermined distance fromthe customer address.

Clause 3. The system of Clause 2, wherein the first predetermineddistance and the second predetermined distance are the same distance.

Clause 4. The system of Clause 2, wherein the second predetermineddistance weighted based upon a geographic location of at least one ofthe customer address or transaction locations.

Clause 5. The system of Clause 1, wherein the first predetermineddistance is weighted based upon a geographic location of at least one ofthe customer address or the transaction locations.

Clause 6. The system of Clause 1, wherein the relocation score isfurther based on a plurality of categories associated with the at leasta portion of the plurality of customer transactions, and wherein theplurality of categories is determined based on merchant category codes.

Clause 7. The system of Clause 1, wherein the transaction locations arebased on locations of point of sale devices (PoS).

Clause 8. The system of Clause 1, wherein the transaction locations arebased on Internet Protocol (IP) addresses associated with digitaltransactions completed using at least a portion of the customer accountinformation.

Clause 9. The system of Clause 1, wherein the duration of time isgreater than 60 days.

Clause 10. The system of Clause 1, wherein the instructions are furtherconfigured to cause the system to receive, at the one or moreprocessors, an indication of a payment to a balance associated with thecustomer account information.

Clause 11. The system of Clause 10, wherein: the indication of thepayment is received via an electronic transaction from an entity; andthe relocation score based on a regionality of the entity.

Clause 12. The system of Clause 10, wherein: the indication of thepayment is received via a check; and the instructions are furtherconfigured to cause the system to: perform optical character recognitionon the check; identify a check address on the check; and update therelocation score based on the check address.

Clause 13. A method for confirming account information, comprising:storing, in a database associated with one or more processors, customeraccount information including a customer address; receiving, at the oneor more processors, transaction data associated with a plurality ofcustomer transactions, the transaction data including transactionlocation identifiers associated with at least a portion of the pluralityof customer transactions; receiving, at the one or more processors andfrom a geographic location sensor on a user device, device location dataassociated with the user device; calculating, via the one or moreprocessors, a relocation score based on the device location data and thetransaction data; and transmitting, via a transceiver associated withthe one or more processors, a notification to the user device seekingconfirmation of the account information when the relocation score isabove a predetermined value.

Clause 14. The method of Clause 13, wherein the relocation score isbased upon at least one of: a quantity of transactions of the pluralityof customer transaction having transaction locations beyond a firstpredetermined distance from the customer address as determined by thetransaction location identifiers; or an elapsed duration of time since acustomer transaction of the plurality of customer transactions wascompleted within the first predetermined distance from the customeraddress.

Clause 15. The method of Clause 13, wherein the relocation score isbased upon a duration of time the user device is beyond a firstpredetermined distance from the customer address.

Clause 16. The method of Clause 13, wherein the relocation score isdistance based and the relocation score is adjusted based on ageographic location of at least one of the customer address, transactionlocations associated with the transaction location identifiers, or thedevice location data.

Clause 17. The method of Clause 16, wherein the transaction locationsare based on locations of point of sale devices (PoS).

Clause 18. The method of Clause 16, wherein the transaction locationsare based on Internet Protocol (IP) addresses associated with digitaltransactions completed using at least a portion of the customer accountinformation.

Clause 19. The method of Clause 13, wherein the relocation score isfurther based on a plurality of categories associated with the at leasta portion of the plurality of customer transactions, and wherein theplurality of categories is determined based on merchant category codes.

Clause 20. A system for confirming account information, comprising: oneor more processors; and memory in communication with the one or moreprocessors and storing instructions that, when executed by the one ormore processors, are configured to cause the system to: store, in adatabase associated with the one or more processors, customer accountinformation including a customer address; calculate, via the one or moreprocessors, a relocation score based on device location data receivedfrom a user device and transaction data; receive, at the one or moreprocessors, an indication of a payment to a balance associated with thecustomer account information, the indication of the payment received viaa check; perform, via the one or more processors, optical characterrecognition on the check to identify a check address; update, via theone or more processors, the relocation score based on the check address;and transmit, via a transceiver associated with the one or moreprocessors, a notification to the user device seeking confirmation ofthe account information when the relocation score is above apredetermined value.

Exemplary Use Cases

The following exemplary use cases describe examples of a typical userflow pattern. They are intended solely for explanatory purposes and notlimitation.

Jim has a credit card account at Company A, and his registered addressis 123 Elm Street, Atlanta, Ga. Company A tracks Jim's credit card usage(or receives updates from a third party who tracks Jim's credit cardusage) and updates his statement accordingly, and his expenditures aretypically within 50 miles of his home address. After 5 weeks, Company Acalculates that Jim has used his credit card 20 times outside of a 50mile radius of his registered address. Since not one of those 20transactions were within the 50-mile radius, Company A calculates arelocation score that indicates there is a high certainty that Jim hasmoved. Therefore, Jim may not be receiving his paper bill and Company Amay not receive payment for the prior statement(s). Company A thereforesends Jim a push notification via Company A's mobile application askingif his address has changed. Jim selects yes within the mobileapplication and is prompted to input his new address.

This example fact pattern shows the improvement of the presentlydescribed systems over the prior, manual systems of waiting until acustomer does not pay a bill for several months before contacting thecustomer. Instead, Jim received the push notification with only thepossibility of one monthly statement being missed.

In the same fact pattern as above, Company A has a tiered system oftracking customer movement. When location information is based solely ontransaction location data, as described above for Jim, the maximumrelocation score is 50%. Anything under 50% receives some form ofautomated notification. However, Company A also tracks location datausing the Company A mobile application. Over the course of those 5weeks, Company A also tracks that Jim's mobile device was outside of the50 mile radius and never re-entered the radius. In view of this, Jim'srelocations score increased to over 50% (now 85%) and he receives a callfrom customer service. This example fact pattern shows the improvementof the presently described systems over the prior, manual as they canselectively calculate which customers deserve a manual phone call fromcustomer service and which accounts can suffice with receiving anautomatic notification.

In a final fact pattern for Jim, the 20 credit card transactions outsideof the 50-mile radius total over $2000. Company A has a threshold forhow much can be spent from an account outside of the predetermineddistance from the customer address; Company A sets the threshold at$2000 over any rolling two month period. In view of this, Company Aflags Jim as either potentially moving or a case of potential fraud. Inthis scenario, Company A temporarily deactivates the credit card accountand calls Jim directly to inquire about whether his spending andlocation information are indicative of a potential relocation.

In another fact pattern, Jane has a credit card account at Company B,and her registered address is 647 Main Street, Richmond, Va. Company Btracks Jane's credit card usage and updates her statement accordingly.Typically, Jane sends a check each month from her checking account withBank Y, which is based in Arlington, Va. and has an East Coast regionalfootprint. One month, Company B receives a check from Jane to pay forher credit card statement, and Company B identifies that the routingnumber on the check is from Bank Z, which only has branches inCalifornia. Company B calculates a high relocation score based on thisinformation, and immediately (a) places a hold on Jane's billing and (b)calls Jane with a live customer service agent. Jane confirms she hasmoved, and the customer service agent updates Jane's billing address andremoves the hold.

1. A system for confirming account information, comprising: one or moreprocessors; and memory in communication with the one or more processorsand storing instructions that, when executed by the one or moreprocessors, are configured to cause the system to: store, in a databaseassociated with the system, customer account information including acustomer address; receive transaction data associated with a pluralityof customer transactions, the transaction data including transactionlocation identifiers associated with at least a portion of the pluralityof customer transactions; receive, from a geographic location sensor ona user device, device location data associated with the user device;calculate a relocation score based on the transaction data, wherein therelocation score is based upon: a quantity of transactions of theplurality of customer transaction having transaction locations beyond afirst predetermined distance from the customer address as determined bythe transaction location identifiers; an elapsed duration of time sincea customer transaction of the plurality of customer transactions wascompleted within the first predetermined distance from the customeraddress; and a duration of time the user device is beyond a secondpredetermined distance from the customer address, as determined by thedevice location data; and transmit, via a transceiver associated withthe system, a notification to the user device seeking confirmation ofthe account information when the relocation score is above apredetermined value.
 2. (canceled)
 3. The system of claim 1, wherein thefirst predetermined distance and the second predetermined distance arethe same distance.
 4. The system of claim 1, wherein the secondpredetermined distance is weighted based upon a geographic location ofat least one of the customer address or transaction locations.
 5. Thesystem of claim 1, wherein the first predetermined distance is weightedbased upon a geographic location of at least one of the customer addressor the transaction locations.
 6. The system of claim 1, wherein therelocation score is further based on a plurality of categoriesassociated with the at least a portion of the plurality of customertransactions, and wherein the plurality of categories is determinedbased on merchant category codes.
 7. The system of claim 1, wherein thetransaction locations are based on locations of point of sale devices(PoS).
 8. The system of claim 1, wherein the transaction locations arebased on Internet Protocol (IP) addresses associated with digitaltransactions completed using at least a portion of the customer accountinformation.
 9. The system of claim 1, wherein the duration of time isgreater than 60 days.
 10. The system of claim 1, wherein theinstructions are further configured to cause the system to receive, atthe one or more processors, an indication of a payment to a balanceassociated with the customer account information.
 11. The system ofclaim 10, wherein: the indication of the payment is received via anelectronic transaction from an entity; and the relocation score based ona regionality of the entity.
 12. The system of claim 10, wherein: theindication of the payment is received via a check; and the instructionsare further configured to cause the system to: perform optical characterrecognition on the check; identify a check address on the check; andupdate the relocation score based on the check address.
 13. A method forconfirming account information, comprising: storing, in a databaseassociated with one or more processors, customer account informationincluding a customer address; receiving, at the one or more processors,transaction data associated with a plurality of customer transactions,the transaction data including transaction location identifiersassociated with at least a portion of the plurality of customertransactions; receiving, at the one or more processors and from ageographic location sensor on a user device, device location dataassociated with the user device; calculating, via the one or moreprocessors, a relocation score based on the device location data and thetransaction data, the relocation score being determined based on anelapsed duration of time since a customer transaction of the pluralityof customer transactions was completed within a first predetermineddistance from the customer address and a duration of time the device isbeyond the first predetermined distance; and transmitting, via atransceiver associated with the one or more processors, a notificationto the user mobile device seeking confirmation of the accountinformation when the relocation score is above a predetermined value.14. The method of claim 13, wherein the relocation score is based uponat least one of: a quantity of transactions of the plurality of customertransaction having transaction locations beyond the first predetermineddistance from the customer address as determined by the transactionlocation identifiers.
 15. (canceled)
 16. The method of claim 13, whereinthe relocation score is location based, and the relocation score isweighted based on a geographic location of at least one of the customeraddress.
 17. The method of claim 16, wherein the transaction locationsare based on locations of point of sale devices (PoS).
 18. The method ofclaim 16, wherein the transaction locations are based on InternetProtocol (IP) addresses associated with digital transactions completedusing at least a portion of the customer account information.
 19. Themethod of claim 13, wherein the relocation score is further based on aplurality of categories associated with the at least a portion of theplurality of customer transactions, and wherein the plurality ofcategories is determined based on merchant category codes. 20.(canceled)